fix: regenerate dependents.json so build-tools dry-run covers all consumers#125
Open
gethinwebster wants to merge 1 commit into
Open
fix: regenerate dependents.json so build-tools dry-run covers all consumers#125gethinwebster wants to merge 1 commit into
gethinwebster wants to merge 1 commit into
Conversation
…mers The committed dependents.json had gone stale: build-tools listed only the components family, so collection-hooks/component-toolkit/test-utils/theming-core were skipped in build-tools dry-runs entirely. Regenerated from current package.json manifests via generate-dependencies.js.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Regenerates the committed
create-build-tree/generated/dependents.json(anddependencies.json), which had gone stale. build-tools listed only the components family as dependents, so collection-hooks / component-toolkit / test-utils / theming-core were skipped entirely in build-tools dry-runs — theirbuild-repositoryjobs never ran. Regenerated from current package.json manifests viagenerate-dependencies.jsso build-tools fans out to all real consumers.Complements the repin fix in #123: #123 makes the consumers that do run resolve the changed package faithfully; this makes sure the right consumers run at all.
How has this been tested?
node generate-dependencies.jsagainst current org manifests; verified build-tools now includes collection-hooks/test-utils/theming-core/component-toolkit/demos. Only the generated JSON changed.Note
This is a committed snapshot and will drift again as repos add deps; a scheduled regeneration or drift-guard would prevent recurrence (follow-up).